Product Technical Manager shall be responsible for preparing the Release Plan. Release Plan is based on Roadmap, Product requirements, Constraints (like Budget, Time, Capability, and Architecture/Design etc.), any commitments to Customers and any upcoming industry event. The decision involves balancing opposing forces. On one side, release need to embark as many requirements as possible to satisfy business objectives and customer needs and on the other side, release plan shall account for limited R&D capabilities, constraints of time and budget and technical or architectural considerations.

Another balancing act required when building a release plan is to arbitrate between new innovative features, to differentiate and keep a leading edge, and existing customer requirements – possibly less exciting but required to keep product relevant for the client base.

The release plan needs to be aligned with the product development process or methodology (Agile, Waterfall etc.). The plan can cover Major, Minor, Update or Patch releases. It helps in defining scope and expectation for development and other maintenance projects. It is an operational document that exhaustively details the content of each release.

Release Plan and Roadmap preparation is an iterative process with all the relevant stake holders.

Roles & Responsibilities:

Trigger/Entry Criteria:

Request from Product Strategist/Head to Product Technical Manager for preparation of Release plan.

Exit Criteria:

Release Plan document prepared/updated and approved.